Automatic management of resource sizing

ABSTRACT

A system for providing automatic resource resizing is provided. The system may be configured to maintain a plurality of virtual machine instances. The system may be further configured to receive a request to execute a program code and allocate computing resources for executing the program code on one of the virtual machine instances. The amount of resources allocated for executing the program code may be specified by the request and adjusted as needed.

CROSS-REFERENCE TO OTHER APPLICATIONS

The present application's Applicant previously filed the following U.S.patent application on Sep. 30, 2014:

application Ser. No. Title 14/502,992 THREADING AS A SERVICE

Further, the present application's Applicant is concurrently filing thefollowing U.S. patent application on Dec. 5, 2014:

application Ser. No. Title 14/562,601 AUTOMATIC DETERMINATION OFRESOURCE SIZING

The disclosures of the above-referenced applications are herebyincorporated by reference in their entireties.

BACKGROUND

Generally described, computing devices utilize a communication network,or a series of communication networks, to exchange data. Companies andorganizations operate computer networks that interconnect a number ofcomputing devices to support operations or provide services to thirdparties. The computing systems can be located in a single geographiclocation or located in multiple, distinct geographic locations (e.g.,interconnected via private or public communication networks).Specifically, data centers or data processing centers, herein generallyreferred to as a “data center,” may include a number of interconnectedcomputing systems to provide computing resources to users of the datacenter. The data centers may be private data centers operated on behalfof an organization or public data centers operated on behalf, or for thebenefit of, the general public.

To facilitate increased utilization of data center resources,virtualization technologies may allow a single physical computing deviceto host one or more instances of virtual machines that appear andoperate as independent computing devices to users of a data center. Withvirtualization, the single physical computing device can create,maintain, delete, or otherwise manage virtual machines in a dynamicmanner. In turn, users can request computer resources from a datacenter, including single computing devices or a configuration ofnetworked computing devices, and be provided with varying numbers ofvirtual machine resources.

In some scenarios, virtual machine instances may be configured accordingto a number of virtual machine instance types to provide specificfunctionality. For example, various computing devices may be associatedwith different combinations of operating systems or operating systemconfigurations, virtualized hardware resources and software applicationsto enable a computing device to provide different desiredfunctionalities, or to provide similar functionalities more efficiently.These virtual machine instance type configurations are often containedwithin a device image, which includes static data containing thesoftware (e.g., the OS and applications together with theirconfiguration and data files, etc.) that the virtual machine will runonce started. The device image is typically stored on the disk used tocreate or initialize the instance. Thus, a computing device may processthe device image in order to implement the desired softwareconfiguration.

BRIEF DESCRIPTION OF THE DRAWINGS

The foregoing aspects and many of the attendant advantages of thisdisclosure will become more readily appreciated as the same becomebetter understood by reference to the following detailed description,when taken in conjunction with the accompanying drawings, wherein:

FIG. 1 is a block diagram depicting an illustrative environment forproviding low latency compute capacity, according to an example aspect.

FIG. 2 depicts a general architecture of a computing device providing aresource manager for managing low latency compute capacity, according toan example aspect.

FIG. 3 is a flow diagram illustrating a resource sizing routineimplemented by a resource manager, according to an example aspect.

FIG. 4 is a flow diagram illustrating a resource sizing routineimplemented by a resource manager, according to another example aspect.

FIG. 5 is a flow diagram illustrating a resource sizing routineimplemented by a resource manager, according to another example aspect.

FIGS. 6-8 illustrate a resource sizing performed by a resource manager,according to an example aspect.

FIGS. 9-11 illustrate a resource sizing performed by a resource manager,according to another example aspect.

DETAILED DESCRIPTION

Companies and organizations no longer need to acquire and manage theirown data centers in order to perform computing operations (e.g., executecode, including threads, programs, functions, software, routines,subroutines, processes, etc.). With the advent of cloud computing,storage space and compute power traditionally provided by hardwarecomputing devices can now be obtained and configured in minutes over theInternet. Thus, developers can quickly purchase a desired amount ofcomputing resources without having to worry about acquiring physicalmachines. Such computing resources are typically purchased in the formof virtual computing resources, or virtual machine instances. Theseinstances of virtual machines are software implementations of physicalmachines (e.g., computers), which are hosted on physical computingdevices, and may contain operating systems and applications that aretraditionally provided on physical machines. These virtual machineinstances are configured with a set of computing resources (e.g.,memory, CPU, disk, network, etc.) that applications running on thevirtual machine instances may request and can be utilized in the samemanner as physical computers.

However, even when virtual computing resources are purchased (e.g., inthe form of virtual machine instances), developers still have to decidehow many and what type of virtual machine instances to purchase, and howlong to keep them. For example, the costs of using the virtual machineinstances may vary depending on the type and the number of hours theyare rented. In addition, the minimum time a virtual machine may berented is typically on the order of hours. Further, developers have tospecify the hardware and software resources (e.g., type of operatingsystems and language runtimes, etc.) to install on the virtual machines.Other concerns that they might have include over-utilization (e.g.,acquiring too little computing resources and suffering performanceissues), under-utilization (e.g., acquiring more computing resourcesthan necessary to run the codes, and thus overpaying), prediction ofchange in traffic (e.g., so that they know when to scale up or down),and instance and language runtime startup delay, which can take 3-10minutes, or longer, even though users may desire computing capacity onthe order of seconds or even milliseconds. Thus, an improved method ofallowing users to take advantage of the virtual machine instancesprovided by service providers is desired.

According to aspects of the present disclosure, by maintaining a pool ofpre-initialized virtual machine instances that are ready for use as soonas a user request is received, delay (sometimes referred to as latency)associated with executing the user code (e.g., instance and languageruntime startup time) can be significantly reduced.

Generally described, aspects of the present disclosure relate to themanagement of virtual machine instances and containers created therein.Specifically, systems and methods are disclosed which facilitatemanagement of virtual machine instances in a virtual compute system. Thevirtual compute system maintains a pool of virtual machine instancesthat have one or more software components (e.g., operating systems,language runtimes, libraries, etc.) loaded thereon. Maintaining the poolof virtual machine instances may involve creating a new instance,acquiring a new instance from an external instance provisioning service,destroying an instance, assigning/reassigning an instance to a user,modifying an instance (e.g., containers or resources therein), etc. Thevirtual machine instances in the pool can be designated to service userrequests to execute program codes. In the present disclosure, thephrases “program code,” “user code,” and “cloud function” may sometimesbe interchangeably used. The program codes can be executed in isolatedcontainers that are created on the virtual machine instances. Since thevirtual machine instances in the pool have already been booted andloaded with particular operating systems and language runtimes by thetime the requests are received, the delay associated with findingcompute capacity that can handle the requests (e.g., by executing theuser code in one or more containers created on the virtual machineinstances) is significantly reduced.

In another aspect, a virtual compute system may monitor and loginformation related to the amount of resources allocated for executinguser code. By doing so, the virtual compute system may be able toidentify opportunities for improving the performance of the user codeexecution by adjusting the amount of allocated resources. Error ratesmay be reduced by increasing the amount of allocated resources in theevent of over-utilization, and costs associated with executing the usercode may be reduced by decreasing the amount of allocated resources inthe event of under-utilization.

Specific embodiments and example applications of the present disclosurewill now be described with reference to the drawings. These embodimentsand example applications are intended to illustrate, and not limit, thepresent disclosure.

With reference to FIG. 1, a block diagram illustrating an embodiment ofa virtual environment 100 will be described. The example shown in FIG. 1includes a virtual environment 100 in which users (e.g., developers,etc.) of user computing devices 102 may run various program codes usingthe virtual computing resources provided by a virtual compute system110.

By way of illustration, various example user computing devices 102 areshown in communication with the virtual compute system 110, including adesktop computer, laptop, and a mobile phone. In general, the usercomputing devices 102 can be any computing device such as a desktop,laptop, mobile phone (or smartphone), tablet, kiosk, wireless device,and other electronic devices. In addition, the user computing devices102 may include web services running on the same or different datacenters, where, for example, different web services may programmaticallycommunicate with each other to perform one or more techniques describedherein. Further, the user computing devices 102 may include Internet ofThings (IoT) devices such as Internet appliances and connected devices.The virtual compute system 110 may provide the user computing devices102 with one or more user interfaces, command-line interfaces (CLI),application programming interfaces (API), and/or other programmaticinterfaces for generating and uploading user codes, invoking the usercodes (e.g., submitting a request to execute the user codes on thevirtual compute system 110), scheduling event-based jobs or timed jobs,tracking the user codes, and/or viewing other logging or monitoringinformation related to their requests and/or user codes. Although one ormore embodiments may be described herein as using a user interface, itshould be appreciated that such embodiments may, additionally oralternatively, use any CLIs, APIs, or other programmatic interfaces.

The user computing devices 102 access the virtual compute system 110over a network 104. The network 104 may be any wired network, wirelessnetwork, or combination thereof. In addition, the network 104 may be apersonal area network, local area network, wide area network,over-the-air broadcast network (e.g., for radio or television), cablenetwork, satellite network, cellular telephone network, or combinationthereof. For example, the network 104 may be a publicly accessiblenetwork of linked networks, possibly operated by various distinctparties, such as the Internet. In some embodiments, the network 104 maybe a private or semi-private network, such as a corporate or universityintranet. The network 104 may include one or more wireless networks,such as a Global System for Mobile Communications (GSM) network, a CodeDivision Multiple Access (CDMA) network, a Long Term Evolution (LTE)network, or any other type of wireless network. The network 104 can useprotocols and components for communicating via the Internet or any ofthe other aforementioned types of networks. For example, the protocolsused by the network 104 may include Hypertext Transfer Protocol (HTTP),HTTP Secure (HTTPS), Message Queue Telemetry Transport (MQTT),Constrained Application Protocol (CoAP), and the like. Protocols andcomponents for communicating via the Internet or any of the otheraforementioned types of communication networks are well known to thoseskilled in the art and, thus, are not described in more detail herein.

The virtual compute system 110 is depicted in FIG. 1 as operating in adistributed computing environment including several computer systemsthat are interconnected using one or more computer networks. The virtualcompute system 110 could also operate within a computing environmenthaving a fewer or greater number of devices than are illustrated inFIG. 1. Thus, the depiction of the virtual compute system 110 in FIG. 1should be taken as illustrative and not limiting to the presentdisclosure. For example, the virtual compute system 110 or variousconstituents thereof could implement various Web services components,hosted or “cloud” computing environments, and/or peer-to-peer networkconfigurations to implement at least a portion of the processesdescribed herein.

Further, the virtual compute system 110 may be implemented in hardwareand/or software and may, for instance, include one or more physical orvirtual servers implemented on physical computer hardware configured toexecute computer executable instructions for performing various featuresthat will be described herein. The one or more servers may begeographically dispersed or geographically co-located, for instance, inone or more data centers.

In the environment illustrated FIG. 1, the virtual environment 100includes a virtual compute system 110, which includes a frontend 120, awarming pool manager 130, a worker manager 140, and a resource manager150. In the depicted example, virtual machine instances (“instances”)152, 154 are shown in a warming pool 130A managed by the warming poolmanager 130, and instances 156, 157, 158, 159 are shown in an activepool 140A managed by the worker manager 140. The illustration of thevarious components within the virtual compute system 110 is logical innature and one or more of the components can be implemented by a singlecomputing device or multiple computing devices. For example, theinstances 152, 154, 156, 157, 158, 159 can be implemented on one or morephysical computing devices in different various geographic regions.Similarly, each of the frontend 120, the warming pool manager 130, theworker manager 140, and the resource manager 150 can be implementedacross multiple physical computing devices. Alternatively, one or moreof the frontend 120, the warming pool manager 130, the worker manager140, and the resource manager 150 can be implemented on a singlephysical computing device. In some embodiments, the virtual computesystem 110 may comprise multiple frontends, multiple warming poolmanagers, multiple worker managers, and/or multiple capacity managers.Although six virtual machine instances are shown in the example of FIG.1, the embodiments described herein are not limited as such, and oneskilled in the art will appreciate that the virtual compute system 110may comprise any number of virtual machine instances implemented usingany number of physical computing devices. Similarly, although a singlewarming pool and a single active pool are shown in the example of FIG.1, the embodiments described herein are not limited as such, and oneskilled in the art will appreciate that the virtual compute system 110may comprise any number of warming pools and active pools.

In the example of FIG. 1, the virtual compute system 110 is illustratedas being connected to the network 104. In some embodiments, any of thecomponents within the virtual compute system 110 can communicate withother components (e.g., the user computing devices 102 and auxiliaryservices 106, which may include monitoring/logging/billing services 107,storage service 108, an instance provisioning service 109, and/or otherservices that may communicate with the virtual compute system 110) ofthe virtual environment 100 via the network 104. In other embodiments,not all components of the virtual compute system 110 are capable ofcommunicating with other components of the virtual environment 100. Inone example, only the frontend 120 may be connected to the network 104,and other components of the virtual compute system 110 may communicatewith other components of the virtual environment 100 via the frontend120.

Users may use the virtual compute system 110 to execute user codethereon. For example, a user may wish to run a piece of code inconnection with a web or mobile application that the user has developed.One way of running the code would be to acquire virtual machineinstances from service providers who provide infrastructure as aservice, configure the virtual machine instances to suit the user'sneeds, and use the configured virtual machine instances to run the code.Alternatively, the user may send a code execution request to the virtualcompute system 110. The virtual compute system 110 can handle theacquisition and configuration of compute capacity (e.g., containers,instances, etc., which are described in greater detail below) based onthe code execution request, and execute the code using the computecapacity. The virtual compute system 110 may automatically scale up anddown based on the volume, thereby relieving the user from the burden ofhaving to worry about over-utilization (e.g., acquiring too littlecomputing resources and suffering performance issues) orunder-utilization (e.g., acquiring more computing resources thannecessary to run the codes, and thus overpaying).

The frontend 120 processes all the requests to execute user code on thevirtual compute system 110. In one embodiment, the frontend 120 servesas a front door to all the other services provided by the virtualcompute system 110. The frontend 120 processes the requests and makessure that the requests are properly authorized. For example, thefrontend 120 may determine whether the user associated with the requestis authorized to access the user code specified in the request.

The user code as used herein may refer to any program code (e.g., aprogram, routine, subroutine, thread, etc.) written in a specificprogram language. In the present disclosure, the terms “code,” “usercode,” and “program code,” may be used interchangeably. Such user codemay be executed to achieve a specific task, for example, in connectionwith a particular web application or mobile application developed by theuser. For example, the user codes may be written in JavaScript(node.js), Java, Python, and/or Ruby. The request may include the usercode (or the location thereof) and one or more arguments to be used forexecuting the user code. For example, the user may provide the user codealong with the request to execute the user code. In another example, therequest may identify a previously uploaded program code (e.g., using theAPI for uploading the code) by its name or its unique ID. In yet anotherexample, the code may be included in the request as well as uploaded ina separate location (e.g., the storage service 108 or a storage systeminternal to the virtual compute system 110) prior to the request isreceived by the virtual compute system 110. The virtual compute system110 may vary its code execution strategy based on where the code isavailable at the time the request is processed.

The frontend 120 may receive the request to execute such user codes inresponse to Hypertext Transfer Protocol Secure (HTTPS) requests from auser. Also, any information (e.g., headers and parameters) included inthe HTTPS request may also be processed and utilized when executing theuser code. As discussed above, any other protocols, including, forexample, HTTP, MQTT, and CoAP, may be used to transfer the messagecontaining the code execution request to the frontend 120. The frontend120 may also receive the request to execute such user codes when anevent is detected, such as an event that the user has registered totrigger automatic request generation. For example, the user may haveregistered the user code with an auxiliary service 106 and specifiedthat whenever a particular event occurs (e.g., a new file is uploaded),the request to execute the user code is sent to the frontend 120.Alternatively, the user may have registered a timed job (e.g., executethe user code every 24 hours). In such an example, when the scheduledtime arrives for the timed job, the request to execute the user code maybe sent to the frontend 120. In yet another example, the frontend 120may have a queue of incoming code execution requests, and when theuser's batch job is removed from the virtual compute system's workqueue, the frontend 120 may process the user request. In yet anotherexample, the request may originate from another component within thevirtual compute system 110 or other servers or services not illustratedin FIG. 1.

A user request may specify one or more third-party libraries (includingnative libraries) to be used along with the user code. In oneembodiment, the user request is a ZIP file containing the user code andany libraries (and/or identifications of storage locations thereof). Insome embodiments, the user request includes metadata that indicates theprogram code to be executed, the language in which the program code iswritten, the user associated with the request, and/or the computingresources (e.g., memory, CPU, storage, network packets, etc.) to bereserved for executing the program code. For example, the program codemay be provided with the request, previously uploaded by the user,provided by the virtual compute system 110 (e.g., standard routines),and/or provided by third parties. In some embodiments, resource-levelconstraints (e.g., how much memory is to be allocated for executing aparticular user code) are specified for the particular user code, andmay not vary over each execution of the user code. In such cases, thevirtual compute system 110 may have access to such resource-levelconstraints before each individual request is received, and theindividual requests may not specify such resource-level constraints. Insome embodiments, the resource-level constraints are adjusted over timeand may vary across different executions of a single program code. Forexample, the same program code may be used to process two different setsof data, where one set of data requires more resources than the other.In such a case, the user may specify different resource constraints forthe two different executions or the virtual compute system 110 mayautomatically adjust the amount of resources allocated to each executionof the program code based on spatial (e.g., in other parts of thevirtual compute system 110) or historical (e.g., over time) trends forthe user and/or program code. In some embodiments, the user request mayspecify other constraints such as permission data that indicates whatkind of permissions that the request has to execute the user code. Suchpermission data may be used by the virtual compute system 110 to accessprivate resources (e.g., on a private network).

In some embodiments, the user request may specify the behavior thatshould be adopted for handling the user request. In such embodiments,the user request may include an indicator for enabling one or moreexecution modes in which the user code associated with the user requestis to be executed. For example, the request may include a flag or aheader for indicating whether the user code should be executed in adebug mode in which the debugging and/or logging output that may begenerated in connection with the execution of the user code is providedback to the user (e.g., via a console user interface). In such anexample, the virtual compute system 110 may inspect the request and lookfor the flag or the header, and if it is present, the virtual computesystem 110 may modify the behavior (e.g., logging facilities) of thecontainer in which the user code is executed, and cause the output datato be provided back to the user. In some embodiments, the behavior/modeindicators are added to the request by the user interface provided tothe user by the virtual compute system 110. Other features such assource code profiling, remote debugging, etc. may also be enabled ordisabled based on the indication provided in the request.

In some embodiments, the virtual compute system 110 may include multiplefrontends 120. In such embodiments, a load balancer may be provided todistribute the incoming requests to the multiple frontends 120, forexample, in a round-robin fashion. In some embodiments, the manner inwhich the load balancer distributes incoming requests to the multiplefrontends 120 may be based on the state of the warming pool 130A and/orthe active pool 140A. For example, if the capacity in the warming pool130A is deemed to be sufficient, the requests may be distributed to themultiple frontends 120 based on the individual capacities of thefrontends 120 (e.g., based on one or more load balancing restrictions).On the other hand, if the capacity in the warming pool 130A is less thana threshold amount, one or more of such load balancing restrictions maybe removed such that the requests may be distributed to the multiplefrontends 120 in a manner that reduces or minimizes the number ofvirtual machine instances taken from the warming pool 130A. For example,even if, according to a load balancing restriction, a request is to berouted to Frontend A, if Frontend A needs to take an instance out of thewarming pool 130A to service the request but Frontend B can use one ofthe instances in its active pool to service the same request, therequest may be routed to Frontend B.

The warming pool manager 130 ensures that virtual machine instances areready to be used by the worker manager 140 when the virtual computesystem 110 receives a request to execute user code on the virtualcompute system 110. In the example illustrated in FIG. 1, the warmingpool manager 130 manages the warming pool 130A, which is a group(sometimes referred to as a pool) of pre-initialized and pre-configuredvirtual machine instances that may be used to service incoming user codeexecution requests. In some embodiments, the warming pool manager 130causes virtual machine instances to be booted up on one or more physicalcomputing machines within the virtual compute system 110 and added tothe warming pool 130A. In other embodiments, the warming pool manager130 communicates with an auxiliary virtual machine instance service(e.g., the instance provisioning service 109 of FIG. 1) to create andadd new instances to the warming pool 130A. In some embodiments, thewarming pool manager 130 may utilize both physical computing deviceswithin the virtual compute system 110 and one or more virtual machineinstance services to acquire and maintain compute capacity that can beused to service code execution requests received by the frontend 120. Insome embodiments, the virtual compute system 110 may comprise one ormore logical knobs or switches for controlling (e.g., increasing ordecreasing) the available capacity in the warming pool 130A. Forexample, a system administrator may use such a knob or switch toincrease the capacity available (e.g., the number of pre-bootedinstances) in the warming pool 130A during peak hours. In someembodiments, virtual machine instances in the warming pool 130A can beconfigured based on a predetermined set of configurations independentfrom a specific user request to execute a user's code. The predeterminedset of configurations can correspond to various types of virtual machineinstances to execute user codes. The warming pool manager 130 canoptimize types and numbers of virtual machine instances in the warmingpool 130A based on one or more metrics related to current or previoususer code executions.

As shown in FIG. 1, instances may have operating systems (OS) and/orlanguage runtimes loaded thereon. For example, the warming pool 130Amanaged by the warming pool manager 130 comprises instances 152, 154.The instance 152 includes an OS 152A and a runtime 152B. The instance154 includes an OS 154A. In some embodiments, the instances in thewarming pool 130A may also include containers (which may further containcopies of operating systems, runtimes, user codes, etc.), which aredescribed in greater detail below. Although the instance 152 is shown inFIG. 1 to include a single runtime, in other embodiments, the instancesdepicted in FIG. 1 may include two or more runtimes, each of which maybe used for running a different user code. In some embodiments, thewarming pool manager 130 may maintain a list of instances in the warmingpool 130A. The list of instances may further specify the configuration(e.g., OS, runtime, container, etc.) of the instances.

In some embodiments, the virtual machine instances in the warming pool130A may be used to serve any user's request. In one embodiment, all thevirtual machine instances in the warming pool 130A are configured in thesame or substantially similar manner. In another embodiment, the virtualmachine instances in the warming pool 130A may be configured differentlyto suit the needs of different users. For example, the virtual machineinstances may have different operating systems, different languageruntimes, and/or different libraries loaded thereon. In yet anotherembodiment, the virtual machine instances in the warming pool 130A maybe configured in the same or substantially similar manner (e.g., withthe same OS, language runtimes, and/or libraries), but some of thoseinstances may have different container configurations. For example, twoinstances may have runtimes for both Python and Ruby, but one instancemay have a container configured to run Python code, and the otherinstance may have a container configured to run Ruby code. In someembodiments, multiple warming pools 130A, each havingidentically-configured virtual machine instances, are provided.

The warming pool manager 130 may pre-configure the virtual machineinstances in the warming pool 130A, such that each virtual machineinstance is configured to satisfy at least one of the operatingconditions that may be requested or specified by the user request toexecute program code on the virtual compute system 110. In oneembodiment, the operating conditions may include program languages inwhich the potential user codes may be written. For example, suchlanguages may include Java, JavaScript, Python, Ruby, and the like. Insome embodiments, the set of languages that the user codes may bewritten in may be limited to a predetermined set (e.g., set of 4languages, although in some embodiments sets of more or less than fourlanguages are provided) in order to facilitate pre-initialization of thevirtual machine instances that can satisfy requests to execute usercodes. For example, when the user is configuring a request via a userinterface provided by the virtual compute system 110, the user interfacemay prompt the user to specify one of the predetermined operatingconditions for executing the user code. In another example, theservice-level agreement (SLA) for utilizing the services provided by thevirtual compute system 110 may specify a set of conditions (e.g.,programming languages, computing resources, etc.) that user requestsshould satisfy, and the virtual compute system 110 may assume that therequests satisfy the set of conditions in handling the requests. Inanother example, operating conditions specified in the request mayinclude: the amount of compute power to be used for processing therequest; the type of the request (e.g., HTTP vs. a triggered event); thetimeout for the request (e.g., threshold time after which the requestmay be terminated); security policies (e.g., may control which instancesin the warming pool 130A are usable by which user); and etc.

The worker manager 140 manages the instances used for servicing incomingcode execution requests. In the example illustrated in FIG. 1, theworker manager 140 manages the active pool 140A, which is a group(sometimes referred to as a pool) of virtual machine instances that arecurrently assigned to one or more users. Although the virtual machineinstances are described here as being assigned to a particular user, insome embodiments, the instances may be assigned to a group of users,such that the instance is tied to the group of users and any member ofthe group can utilize resources on the instance. For example, the usersin the same group may belong to the same security group (e.g., based ontheir security credentials) such that executing one member's code in acontainer on a particular instance after another member's code has beenexecuted in another container on the same instance does not posesecurity risks. Similarly, the worker manager 140 may assign theinstances and the containers according to one or more policies thatdictate which requests can be executed in which containers and whichinstances can be assigned to which users. An example policy may specifythat instances are assigned to collections of users who share the sameaccount (e.g., account for accessing the services provided by thevirtual compute system 110). In some embodiments, the requestsassociated with the same user group may share the same containers (e.g.,if the user codes associated therewith are identical). In someembodiments, a request does not differentiate between the differentusers of the group and simply indicates the group to which the usersassociated with the requests belong.

In the example illustrated in FIG. 1, user codes are executed inisolated compute systems referred to as containers. Containers arelogical units created within a virtual machine instance using theresources available on that instance. For example, the worker manager140 may, based on information specified in the request to execute usercode, create a new container or locate an existing container in one ofthe instances in the active pool 140A and assigns the container to therequest to handle the execution of the user code associated with therequest. In one embodiment, such containers are implemented as Linuxcontainers. The virtual machine instances in the active pool 140A mayhave one or more containers created thereon and have one or more programcodes associated with the user loaded thereon (e.g., either in one ofthe containers or in a local cache of the instance).

As shown in FIG. 1, instances may have operating systems (OS), languageruntimes, and containers. The containers may have individual copies ofthe OS and the language runtimes and user codes loaded thereon. In theexample of FIG. 1, the active pool 140A managed by the worker manager140 includes the instances 156, 157, 158, 159. The instance 156 hascontainers 156A, 156B. The container 156A has OS 156A-1, runtime 156A-2,and code 156A-3 loaded therein. In the depicted example, the container156A has its own OS, runtime, and code loaded therein. In oneembodiment, the OS 156A-1 (e.g., the kernel thereof), runtime 156A-2,and/or code 156A-3 are shared among the containers 156A, 156B (and anyother containers not illustrated in FIG. 1). In another embodiment, theOS 156A-1 (e.g., any code running outside the kernel), runtime 156A-2,and/or code 156A-3 are independent copies that are created for thecontainer 156A and are not shared with other containers on the instance156. In yet another embodiment, some portions of the OS 156A-1, runtime156A-2, and/or code 156A-3 are shared among the containers on theinstance 156, and other portions thereof are independent copies that arespecific to the container 156A. The instance 157 includes containers157A, 157B, 157C, the instance 158 includes a container 158A, and theinstance 159 includes a container 159A.

In the example of FIG. 1, the sizes of the containers depicted in FIG. 1may be proportional to the actual size of the containers. For example,the container 156A occupies more space than the container 156B on theinstance 156. Similarly, the containers 157A, 157B, 157C, 159A may beequally sized, and the container 158A may be larger (e.g., have morecomputing resources allocated thereto) than the containers 157A, 157B,157C, 159A. The dotted boxes labeled “C” shown in the instance 159indicate the space remaining on the instances that may be used to createnew instances. In some embodiments, the sizes of the containers may be64 MB or any multiples thereof. In other embodiments, the sizes of thecontainers may be any arbitrary size smaller than or equal to the sizeof the instances in which the containers are created. In someembodiments, the sizes of the containers may be any arbitrary sizesmaller than, equal to, or larger than the size of the instances inwhich the containers are created. By how much the sizes of thecontainers can exceed the size of the instance may be determined basedon how likely that those containers might be utilized beyond thecapacity provided by the instance. For example, five containers having amemory size of 1 GB (5 GB in total) may be created in an instance havinga memory size of 4 GB. If each of the containers does not reach the fullcapacity of 1 GB, the containers may function properly despite theover-subscription.

Although the components inside the containers 156B, 157A, 157B, 157C,158A, 159A are not illustrated in the example of FIG. 1, each of thesecontainers may have various operating systems, language runtimes,libraries, and/or user code. In some embodiments, instances may haveuser codes loaded thereon (e.g., in an instance-level cache), andcontainers within those instances may also have user codes loadedtherein. In some embodiments, the worker manager 140 may maintain a listof instances in the active pool 140A. The list of instances may furtherspecify the configuration (e.g., OS, runtime, container, etc.) of theinstances. In some embodiments, the worker manager 140 may have accessto a list of instances in the warming pool 130A (e.g., including thenumber and type of instances). In other embodiments, the worker manager140 requests compute capacity from the warming pool manager 130 withouthaving knowledge of the virtual machine instances in the warming pool130A.

After a request has been successfully processed by the frontend 120, theworker manager 140 finds capacity to service the request to execute usercode on the virtual compute system 110. For example, if there exists aparticular virtual machine instance in the active pool 140A that has acontainer with the same user code loaded therein (e.g., code 156A-3shown in the container 156A), the worker manager 140 may assign thecontainer to the request and cause the user code to be executed in thecontainer. Alternatively, if the user code is available in the localcache of one of the virtual machine instances (e.g., stored on theinstance 158 but do not belong to any individual containers), the workermanager 140 may create a new container on such an instance, assign thecontainer to the request, and cause the user code to be loaded andexecuted in the container.

If the worker manager 140 determines that the user code associated withthe request is not found on any of the instances (e.g., either in acontainer or the local cache of an instance) in the active pool 140A,the worker manager 140 may determine whether any of the instances in theactive pool 140A is currently assigned to the user associated with therequest and has compute capacity to handle the current request. If thereis such an instance, the worker manager 140 may create a new containeron the instance and assign the container to the request. Alternatively,the worker manager 140 may further configure an existing container onthe instance assigned to the user, and assign the container to therequest. For example, the worker manager 140 may determine that theexisting container may be used to execute the user code if a particularlibrary demanded by the current user request is loaded thereon. In sucha case, the worker manager 140 may load the particular library and theuser code onto the container and use the container to execute the usercode.

If the active pool 140A does not contain any instances currentlyassigned to the user, the worker manager 140 pulls a new virtual machineinstance from the warming pool 130A, assigns the instance to the userassociated with the request, creates a new container on the instance,assigns the container to the request, and causes the user code to bedownloaded and executed on the container.

In some embodiments, the virtual compute system 110 is adapted to beginexecution of the user code shortly after it is received (e.g., by thefrontend 120). A time period can be determined as the difference in timebetween initiating execution of the user code (e.g., in a container on avirtual machine instance associated with the user) and receiving arequest to execute the user code (e.g., received by a frontend). Thevirtual compute system 110 is adapted to begin execution of the usercode within a time period that is less than a predetermined duration. Inone embodiment, the predetermined duration is 500 ms. In anotherembodiment, the predetermined duration is 300 ms. In another embodiment,the predetermined duration is 100 ms. In another embodiment, thepredetermined duration is 50 ms. In another embodiment, thepredetermined duration is 10 ms. In another embodiment, thepredetermined duration may be any value chosen from the range of 10 msto 500 ms. In some embodiments, the virtual compute system 110 isadapted to begin execution of the user code within a time period that isless than a predetermined duration if one or more conditions aresatisfied. For example, the one or more conditions may include any oneof: (1) the user code is loaded on a container in the active pool 140Aat the time the request is received; (2) the user code is stored in thecode cache of an instance in the active pool 140A at the time therequest is received; (3) the active pool 140A contains an instanceassigned to the user associated with the request at the time the requestis received; or (4) the warming pool 130A has capacity to handle therequest at the time the request is received.

The user code may be downloaded from an auxiliary service 106 such asthe storage service 108 of FIG. 1. Data 108A illustrated in FIG. 1 maycomprise user codes uploaded by one or more users, metadata associatedwith such user codes, or any other data utilized by the virtual computesystem 110 to perform one or more techniques described herein. Althoughonly the storage service 108 is illustrated in the example of FIG. 1,the virtual environment 100 may include other levels of storage systemsfrom which the user code may be downloaded. For example, each instancemay have one or more storage systems either physically (e.g., a localstorage resident on the physical computing system on which the instanceis running) or logically (e.g., a network-attached storage system innetwork communication with the instance and provided within or outsideof the virtual compute system 110) associated with the instance on whichthe container is created. Alternatively, the code may be downloaded froma web-based data store provided by the storage service 108.

Once the worker manager 140 locates one of the virtual machine instancesin the warming pool 130A that can be used to serve the user codeexecution request, the warming pool manager 130 or the worker manager140 takes the instance out of the warming pool 130A and assigns it tothe user associated with the request. The assigned virtual machineinstance is taken out of the warming pool 130A and placed in the activepool 140A. In some embodiments, once the virtual machine instance hasbeen assigned to a particular user, the same virtual machine instancecannot be used to service requests of any other user. This providessecurity benefits to users by preventing possible co-mingling of userresources. Alternatively, in some embodiments, multiple containersbelonging to different users (or assigned to requests associated withdifferent users) may co-exist on a single virtual machine instance. Suchan approach may improve utilization of the available compute capacity.In some embodiments, the virtual compute system 110 may maintain aseparate cache in which user codes are stored to serve as anintermediate level of caching system between the local cache of thevirtual machine instances and a web-based network storage (e.g.,accessible via the network 104).

After the user code has been executed, the worker manager 140 may teardown the container used to execute the user code to free up theresources it occupied to be used for other containers in the instance.Alternatively, the worker manager 140 may keep the container running touse it to service additional requests from the same user. For example,if another request associated with the same user code that has alreadybeen loaded in the container, the request can be assigned to the samecontainer, thereby eliminating the delay associated with creating a newcontainer and loading the user code in the container. In someembodiments, the worker manager 140 may tear down the instance in whichthe container used to execute the user code was created. Alternatively,the worker manager 140 may keep the instance running to use it toservice additional requests from the same user. The determination ofwhether to keep the container and/or the instance running after the usercode is done executing may be based on a threshold time, the type of theuser, average request volume of the user, and/or other operatingconditions. For example, after a threshold time has passed (e.g., 5minutes, 30 minutes, 1 hour, 24 hours, 30 days, etc.) without anyactivity (e.g., running of the code), the container and/or the virtualmachine instance is shutdown (e.g., deleted, terminated, etc.), andresources allocated thereto are released. In some embodiments, thethreshold time passed before a container is torn down is shorter thanthe threshold time passed before an instance is torn down.

In some embodiments, the virtual compute system 110 may provide data toone or more of the auxiliary services 106 as it services incoming codeexecution requests. For example, the virtual compute system 110 maycommunicate with the monitoring/logging/billing services 107. Themonitoring/logging/billing services 107 may include: a monitoringservice for managing monitoring information received from the virtualcompute system 110, such as statuses of containers and instances on thevirtual compute system 110; a logging service for managing logginginformation received from the virtual compute system 110, such asactivities performed by containers and instances on the virtual computesystem 110; and a billing service for generating billing informationassociated with executing user code on the virtual compute system 110(e.g., based on the monitoring information and/or the logginginformation managed by the monitoring service and the logging service).In addition to the system-level activities that may be performed by themonitoring/logging/billing services 107 (e.g., on behalf of the virtualcompute system 110) as described above, the monitoring/logging/billingservices 107 may provide application-level services on behalf of theuser code executed on the virtual compute system 110. For example, themonitoring/logging/billing services 107 may monitor and/or log variousinputs, outputs, or other data and parameters on behalf of the user codebeing executed on the virtual compute system 110. Although shown as asingle block, the monitoring, logging, and billing services 107 may beprovided as separate services. The monitoring/logging/billing services107 may communicate with the resource manager 150 to allow the resourcemanager 150 to determine the appropriate amount of resources to be usedfor executing the various program codes on the virtual compute system150.

In some embodiments, the worker manager 140 may perform health checks onthe instances and containers managed by the worker manager 140 (e.g.,those in the active pool 140A). For example, the health checks performedby the worker manager 140 may include determining whether the instancesand the containers managed by the worker manager 140 have any issues of(1) misconfigured networking and/or startup configuration, (2) exhaustedmemory, (3) corrupted file system, (4) incompatible kernel, and/or anyother problems that may impair the performance of the instances and thecontainers. In one embodiment, the worker manager 140 performs thehealth checks periodically (e.g., every 5 minutes, every 30 minutes,every hour, every 24 hours, etc.). In some embodiments, the frequency ofthe health checks may be adjusted automatically based on the result ofthe health checks. In other embodiments, the frequency of the healthchecks may be adjusted based on user requests. In some embodiments, theworker manager 140 may perform similar health checks on the instancesand/or containers in the warming pool 130A. The instances and/or thecontainers in the warming pool 130A may be managed either together withthose instances and containers in the active pool 140A or separately. Insome embodiments, in the case where the health of the instances and/orthe containers in the warming pool 130A is managed separately from theactive pool 140A, the warming pool manager 130, instead of the workermanager 140, may perform the health checks described above on theinstances and/or the containers in the warming pool 130A.

The resource manager 150 manages the amount of resources allocated forprocessing incoming requests to execute user code on the virtual computesystem 110. For example, the resource manager 150 may communicate withthe frontend 120, the warming pool manager 130, the worker manager 140,and/or the auxiliary services 106 to monitor and manage the computecapacity allocated to (and used by) the various program codes executedon the virtual compute system 110. Although the resource manager 150 isillustrated as a distinct component within the virtual compute system110, part or all of the functionalities of the resource manager 150 maybe performed by the frontend 120, the warming pool manager 130, theworker manager 140, and/or the auxiliary services 106. For example, theresource manager 150 may be implemented entirely within one of the othercomponents of the virtual compute system 110 or in a distributed manneracross the other components of the virtual compute system 110. In theexample of FIG. 1, the resource manager 150 includes resource managementdata 150A. The resource management data 150A may include data regardingthe history of incoming requests (e.g., the volume of incoming requestsassociated with a particular program code, the peak hours during whichthose requests are received, etc.), resource-level constraints specifiedby the incoming requests, the amount of resources allocated to theincoming requests, the portion of the allocated resources actuallyutilized by the incoming requests, and any other characteristics ormetrics that may be used by the resource manager 150 to monitor, log,adjust, improve, and/or optimize the performance (e.g., utilization ofthe allocated resources) of the program codes executed on the virtualcompute system 110. The resource management data 150A may also includeany management policies specified by the users or determined by theresource manager 150 for managing the resources on the virtual computesystem 110, which are described below in greater detail.

As discussed above, the request itself may specify the amount ofcomputing resources (e.g., memory, CPU, storage, network packets, etc.)to be used for executing the program code associated with the request.After such a request has been processed and a virtual machine instancehas been assigned to the user associated with the request, the resourcemanager 150 may allocate the amount of resources specified in therequest to the request by creating a container for the same amount ofresources. For example, if the request specifies that 512 MB of memoryis to be used for executing the program code associated with therequest, the resource manager 150 may create a container having a memorysize of 512 MB on the instance assigned to the user associated with therequest. In some embodiments, other configuration information associatedwith the request, the program code, or the user may specify the amountof computing resources to be used for executing the program code. Suchconfiguration information may be provided to the virtual compute system110 either with the request or separately from the request. The resourcemanager 150 may maintain the amount of resources specified in therequest as a default setting for the particular program code associatedwith the request and use the same amount for any subsequent requeststhat are processed on the virtual compute system 110. In someembodiments, the resource manager 150 may allow one or more subsequentrequests to override such a default setting if the one or moresubsequent requests indicate that a resource amount that is differentfrom the default amount is to be allocated to the one or more subsequentrequests. For example, a subsequent request may indicate that a resourceamount that is 10% above the default amount is to be allocated to thesubsequent request for executing the program code. Upon determining thatthe subsequent request indicates that an alternate amount of resourcesis to be allocated to the subsequent request for executing the programcode, the resource manager 150 allocates the alternate amount ofresources to the subsequent request.

In some embodiments, the amount of resources specified in the requestmay differ from the actual amount of resources allocated to the request.For example, in some scenarios, the virtual compute system 110 mayallocate to the request an amount of resources that is a thresholdpercentage over the amount of resources specified in the request. Inother situations, the virtual compute system 110 may allocate to therequest an amount of resources that is a threshold percentage under theamount of resources specified in the request. Whether to over-subscribeor under-subscribe a particular resource may be determined based on thetype of the particular resource, the user, the request, and/or thephysical hardware (e.g., any tolerance or variance associated therewith)on which the particular resource is provided. In some embodiments, theamount of resources allocated to the request may be less than a maximumvalue (or percentage above the amount specified in the request) and/orgreater than a minimum value (or percentage below the amount specifiedin the request) determined based on the type of the particular resource,the user, the request, and/or the physical hardware (e.g., any toleranceor variance associated therewith) on which the particular resource isprovided.

In some embodiments, the particular type of resource specified in therequest (e.g., memory) serves as a guideline for allocating other typesof resource available on the virtual compute system 110. For example, ifthe request specifies that 512 MB of memory is to be used for executingthe program code associated with the request, and the total (e.g.,physical or virtual maximum) or available (e.g., resources not currentlyoccupied by other containers) amount of memory on the instance assignedto the user is 2 GB, other types of resource (e.g., CPU, storage,network packets, etc.) available on the instance are also allocated inproportionate amounts (e.g., a quarter of the CPU, a quarter of thestorage, a quarter of the network packets, etc. are allocated to thecontainer). On the other hand, if the total or available amount ofmemory on the instance assigned to the user were 1 GB, half the CPU,half the storage, half the network packets would be allocated to thecontainer. In some embodiments, the amount of memory that can bespecified by the request or otherwise allocated to the container rangesfrom 64 MB to 1 GB, in 64 MB increments. In some embodiments, otheramounts may be specified by the request and/or allocated to thecontainer. Although memory is used as an example, any other resource maybe selected and used as a guideline for setting the amount of all theresources to be allocated to process the request (e.g., to execute theprogram code). In some embodiments, a single form of resource (e.g., onethat is easiest to understand, most user-friendly, most basic, largestin absolute number, or smallest in absolute number) is selected to bethe representative for all other forms of resource. The request mayspecify, instead of an amount of a particular type of resource, apercentage that may be used for allocating all the resources.Additionally, the request may specify the amounts of more than oneresource.

In some embodiments, the resource manager 150 may, instead of creating anew container and allocating the specified amount of resources to thecontainer, locate an existing container having the specified amount ofresources and cause the program code to be executed in the existingcontainer. The amount of resources allocated to the existing containerdoes not exactly match the specified amount of resources but is within athreshold percentage of the specified amount of resources. In someembodiments, the resource manager 150 may resize an existing containerby allocating a fewer or greater amount of computing resource(s) anddesignate the existing container having an adjusted resource size tohandle the program code associated with a particular program code.Whether the resource manager 150 can dynamically resize the existingcontainer may depend on the language runtime used by the program code.For example, Java runtime might not allow dynamic resizing, whereasPython runtime might.

After a container having the specified amount of resources has beencreated or located, the program code associated with the request isexecuted in the container. The amount of resources allocated to thecontainer (e.g., requested by the user) and/or the amount of resourcesactually utilized by the program code may be logged (e.g., by themonitoring/logging/billing services 107 and/or the resource manager 150)for further analysis. For example, the logged information may includethe amount of memory, the amount of CPU cycles, the amount of networkpackets, and the amount of storage actually used during one or moreexecutions of the program code in the container. Additionally, thelogged information may include resource utilization, error rates,latency, and any errors or exceptions encountered during the executionof the program code. In some embodiments, any errors that are related tothe amount of resources allocated to the container (e.g., out of memoryexceptions) are tagged with a special marking and further analyzed bythe resource manager 150.

In some embodiments, the resource manager 150 may create, or have accessto, multiple classes of users, and apply different rules for differentclasses of users. For example, for more sophisticated users, morecontrol may be given (e.g., control over individual resourceparameters), whereas for other users, they may be allowed to controlonly a single representative parameter, and other parameters may besized based on the representative parameter.

In some embodiments, the resource manager 150 may, based on theinformation logged by the monitoring/logging/billing services 107 and/orthe resource manager 150, provide some guidance to the user as to whatthe user may do to improve the performance of the program code or toreduce costs associated with executing the program code on the virtualcompute system 110. For example, the resource manager 150 may provide tothe user, after seeing repeated occurrences of out of memory exceptions,an indication that the user appears to be consistently setting thememory (or other resource) too low for running a particular user code.Similarly, after determining that invocations of the particular usercode have chronically used only a small portion of the resourcesallocated to them, the resource manager 150 may provide to the user anindication that the user may be setting the memory (or other resource)too high. The indication may specify the amount by which the particularresource(s) should be adjusted. In some embodiments, such an indicationis provided to the user after a threshold number of errors, exceptions,or other telling conditions (e.g., increased latency) have beenprocessed by the resource manager 150. The resource manager 150 mayprovide the indication via any notification mechanism including email, apush notification service, SMS, a social networking service, etc. Insome embodiments, the indication that a resource sizing adjustment isneeded is provided to the user if the amount by which one or moreresources are to be adjusted exceeds a threshold value or percentage.For example, if the resource manager 150 determines that the memory sizespecified by the user should be increased by 0.5% to achieve better oroptimal performance, the resource manager 150 may not send anotification to the user at all, but if the resource manager 150determines that the memory size specified by the user should beincreased by 10% to achieve better or optimal performance, the resourcemanager 150 may send the notification to the user.

In some embodiments, the resource manager 150 may offer a limitedover-subscription where an execution of the program code is allowed toexceed the request amount of resources. For example, if the requestspecified 64 MB of memory, the resource manager 150 may allow theprogram code to use up to 70 or 80 MB of memory. In such a case, theprogram code may execute successfully, but a notification may beprovided to the user that the program code exceeded the requested amountof memory and that future requests to execute the program code shouldspecify a greater amount of memory. The over-subscription may expireafter a threshold number of usage.

In some embodiments, the virtual compute system 110 may automaticallyadjust the amount of resources allocated to individual code executionrequests. For example, in other embodiments where the user may specifythe resource parameters, if the user fails to specify a proper amount ofresources, the execution of the program code may suffer performanceconsequences. For example, if the request specifies that 64 MB of memoryis to be used for executing a particular program code that actuallyrequires 1 GB to run, the user may run into many problems (e.g., theprogram code may simply fail to execute). If the virtual compute system110 relies on the user to adjust the amount of resources specified inthe request, until the issue is addressed by the user, the virtualcompute system 110 may receive thousands or millions of failed requests.In such a scenario, upon detecting that the amount of resourcesspecified in the request is insufficient, the resource manager 150 mayautomatically adjust the amount of resources allocated to the incomingrequests to execute the particular program code. In some embodiments,such an adjustment is made after a threshold number of errors,exceptions, or other telling conditions (e.g., increased latency) havebeen processed by the resource manager 150. Thus, although the first fewrequests may fail even with the automatic resource adjustments made bythe resource manager 150, subsequent requests may eventually produce thedesired outcomes even without user intervention.

In some embodiments, the resource manager 150 may utilize code-specificcharacteristics to improve the resource sizing for executing individualprogram codes. For example, program codes handling image processingmight require a lot of memory, whereas program codes making databaseaccesses might not require as much memory. In another example, for aparticular program code, 64 MB might be sufficient most of the time, butthe virtual compute system 110 might receive a burst of code executionrequests associated with the user every night at 8 pm, for which theresource manager 150 may allocate more memory to the container and/orinstance handling the requests associated with the user. Suchcode-specific characteristics may be maintained by the resource manager150 and the resource sizing of individual program codes may be adjustedaccordingly.

In some embodiments, the resource manager 150 may initially allocate themaximum amount of resources to the program code, and if the resourcemanager 150 determines, after running the program code, that the programcode is actually using 1/10 of the maximum amount, the resource manager150 may allocate half of the maximum amount to subsequent requests toexecute the program code. If the resource manager 150 still determinesthat the program code is using 1/10 of the maximum amount, the resourcemanager 150 may further cut the amount of resources allocated to theprogram code by half. The resource manager 150 may repeat the processuntil the program code uses a significant portion (e.g., 50%, 75%, oranother threshold value) of the resources allocated to the program code.

In some embodiments, the user may specify a resource management policythat dictates the behavior of the resource manager 150. For example, auser who is really price-conscious may be happy to let occasional errorsgo through, if doing so minimizes his or her costs. Thus, such a usermay prefer not to increase the amount of resources allocated forexecuting his or her program codes, even if the currently specifiedamount of resources occasionally results in out of memory errors. On theother hand, a user who is very error-conscious may be willing to takeany measures in order to avoid errors or mistakes (e.g., out of memoryerrors, a very high latency, or some other problem), from happening.Such a user may prefer to minimize the number of errors his or herprogram code encounters, even if the resources allocated for executingthe program code are sometimes under-utilized. In some embodiments, theuser may specify stop limits (e.g., lower and/or upper limit) for cost,utilization, amount of resources, etc. The user may further qualify suchstop limits such that they are applicable only at specified timeperiods. For example, the user may specify the minimum and maximumamounts of money the user would like to spend to have a program codeexecuted, but the user may further specify that during the last week ofeach quarter the limits are not to be applied.

In some embodiments, the resource manager 150 may selectivelyover-subscribe certain resources if the resource manager 150 determinesthat such resources are not being fully utilized by the code executionrequests. For example, the resource manager 150 may allocate 1 GB ofmemory to five different containers on a virtual machine instance having4 GB of virtual or physical memory. The degree of over-subscription maybe based on how likely it is that those containers created on a singleinstance might collectively exhaust the maximum amount of resources ofthe instance. In some embodiments, the user may be given the option ofchoosing to utilize over-subscribed resources at a reduced cost.

In some embodiments, the request may not specify any resource-levelconstraints, but instead request that the amount of resources beautomatically determined by the virtual compute system 110 and that theamount of resources determined by the virtual compute system 110 becommunicated to the user (e.g., so that the user knows the amount ofresources being allocated to service the user's requests).Alternatively, the request may specify the amount of resources to beused for running the user code, but also indicate that if the virtualcompute system 110 determines that the requested amount of resources canbe over-subscribed (e.g., by sharing it with other users) withoutsignificantly affecting the code execution performance, the virtualcompute system 110 may do so by charging the user less (e.g., less thanwhat the specified amount of resources would normally cost).

In some embodiments, the amount of resources allocated to a particularcontainer is adjusted by contracting or expanding the particularcontainer (e.g., by modifying the amount of resources allocated to theexisting container). Alternatively, the amount of resources may beadjusted by creating a new container having an adjusted amount ofresources and letting the old container die by funneling any futurerequests to the new container. In some embodiments, the resizing isperformed based on the characteristics of the particular languageruntime used by the program code (e.g., some may allow dynamic resourceresizing and others may not).

The resource manager 150 may include a resource sizing unit for sizingthe containers (e.g., determining the amount of resources to beallocated to the containers) to be used to execute the user code, and aresource guidance unit for providing notifications to the user regardinghow the amount of resources should be adjusted, if at all. An exampleconfiguration of the resource manager 150 is described in greater detailbelow with reference to FIG. 2.

FIG. 2 depicts a general architecture of a computing system (referencedas resource manager 150) that manages the virtual machine instances inthe virtual compute system 110. The general architecture of the resourcemanager 150 depicted in FIG. 2 includes an arrangement of computerhardware and software modules that may be used to implement aspects ofthe present disclosure. The resource manager 150 may include many more(or fewer) elements than those shown in FIG. 2. It is not necessary,however, that all of these generally conventional elements be shown inorder to provide an enabling disclosure. As illustrated, the resourcemanager 150 includes a processing unit 190, a network interface 192, acomputer readable medium drive 194, an input/output device interface196, all of which may communicate with one another by way of acommunication bus. The network interface 192 may provide connectivity toone or more networks or computing systems. The processing unit 190 maythus receive information and instructions from other computing systemsor services via the network 104. The processing unit 190 may alsocommunicate to and from memory 180 and further provide outputinformation for an optional display (not shown) via the input/outputdevice interface 196. The input/output device interface 196 may alsoaccept input from an optional input device (not shown).

The memory 180 may contain computer program instructions (grouped asmodules in some embodiments) that the processing unit 190 executes inorder to implement one or more aspects of the present disclosure. Thememory 180 generally includes RAM, ROM and/or other persistent,auxiliary or non-transitory computer-readable media. The memory 180 maystore an operating system 184 that provides computer programinstructions for use by the processing unit 190 in the generaladministration and operation of the resource manager 150. The memory 180may further include computer program instructions and other informationfor implementing aspects of the present disclosure. For example, in oneembodiment, the memory 180 includes a user interface unit 182 thatgenerates user interfaces (and/or instructions therefor) for displayupon a computing device, e.g., via a navigation and/or browsinginterface such as a browser or application installed on the computingdevice. In addition, the memory 180 may include and/or communicate withone or more data repositories (not shown), for example, to access userprogram codes and/or libraries.

In addition to and/or in combination with the user interface unit 182,the memory 180 may include a resource sizing unit 186 and a resourceguidance unit 188 that may be executed by the processing unit 190. Inone embodiment, the user interface unit 182, resource sizing unit 186,and resource guidance unit 188 individually or collectively implementvarious aspects of the present disclosure, e.g., monitoring and loggingthe execution of program codes on the virtual compute system 110,determining the need for adjusting the amount of resources allocated toparticular containers and/or requests, providing notifications to theuser regarding the need to adjust the amount of resources, automaticallyadjusting the amount of resources, etc. as described further below.

The resource sizing unit 186 monitors execution of user code on thevirtual compute system 110, provides containers having specified amountsof resources for executing the user code, and adjusts the amount ofresources allocated to the containers. For example, if the resourcesizing unit 186 determines that requests to execute a particular programcode is consistently getting out of memory errors, the resource sizingunit 186 may increase the amount of memory allocated to subsequentrequests to execute the particular program code. On the other hand, ifthe resource sizing unit 186 determines that requests to execute aparticular program code is consistently using only a fraction of theresources allocated to the requests, the resource sizing unit 186 maydecrease the amount of memory allocated to subsequent requests toexecute the particular program code.

The resource guidance unit 188 provide notifications to the userregarding the need to adjust the amount of resources being allocated toservice the requests associated with the user. For example, thenotifications may indicate that the user is consistently specifying anamount that is too low or too high for executing the particular programcode. The notifications may further specify how the amount of resourcesshould be adjusted for improved or optimal performance.

While the resource sizing unit 186 and the resource guidance unit 188are shown in FIG. 2 as part of the resource manager 150, in otherembodiments, all or a portion of the resource sizing unit 186 and theresource guidance unit 188 may be implemented by other components of thevirtual compute system 110 and/or another computing device. For example,in certain embodiments of the present disclosure, another computingdevice in communication with the virtual compute system 110 may includeseveral modules or components that operate similarly to the modules andcomponents illustrated as part of the resource manager 150.

Turning now to FIG. 3, a routine 300 implemented by one or morecomponents of the virtual compute system 110 (e.g., the resource manager150) will be described. Although routine 300 is described with regard toimplementation by the resource manager 150, one skilled in the relevantart will appreciate that alternative components may implement routine300 or that one or more of the blocks may be implemented by a differentcomponent or in a distributed manner.

At block 302 of the illustrative routine 300, the resource manager 150determines a user-specified amount of a first computing resource basedon a request to execute program code on the virtual compute system 110.For example, the first computing resource may be memory, CPU, diskspace, or any other computing resource that may be used for executingthe program code on the virtual compute system 110. The request toexecute the program code on the virtual compute system 110 may indicatehow much resource is to be allocated for executing the program code.

Next, at block 304, the resource manager 150 determines a correspondingamount of a second computing resource based on the user-specified amountof the first computing resource. For example, the resource manager 150may determine the corresponding amount of the second computing resourceby calculating the ratio between the user-specified amount of the firstcomputing resource and the maximum amount of the first computingresource available to be allocated to the request. If the user-specifiedamount is 512 MB of memory, and the maximum amount of memory availableto be allocated to the request is 1 GB, the resource manager 150 maydetermine that the corresponding amount should be one half of themaximum amount of the second computing resource available to beallocated to the request. For example, if the second computing resourceis disk space and 8 GB of disk space is available for allocation, theresource manager 150 may determine that the corresponding amount shouldbe 4 GB.

At block 306, the resource manager 150 allocates the user-specifiedamount of the first computing resource (e.g., memory) and thecorresponding amount of the second computing resource (e.g., disk space)to the request for executing the program code. In the example above, theresource manager 150 may create a container on one of the virtualmachine instances available on the virtual compute system, where thecontainer is allocated 512 MB of memory and 4 GB of disk space. Althoughfirst and second computing resources are used in the example of FIG. 3,additional resources may be used, and such additional resources may alsobe sized according to the ratio between the user-specified amount andthe maximum amount of the first computing resource.

While the routine 300 of FIG. 3 has been described above with referenceto blocks 302-306, the embodiments described herein are not limited assuch, and one or more blocks may be omitted, modified, or switchedwithout departing from the spirit of the present disclosure.

Turning now to FIG. 4, a routine 400 implemented by one or morecomponents of the virtual compute system 110 (e.g., the resource manager150) will be described. Although routine 400 is described with regard toimplementation by the resource manager 150, one skilled in the relevantart will appreciate that alternative components may implement routine400 or that one or more of the blocks may be implemented by a differentcomponent or in a distributed manner.

At block 402 of the illustrative routine 400, the resource manager 150determines a user-specified amount of a computing resource based on arequest to execute program code on the virtual compute system 110. Forexample, the computing resource may be memory, CPU, disk space, or anyother computing resource that may be used for executing the program codeon the virtual compute system 110. The user-specified amount may be anamount of a particular resource (e.g., memory) that is indicated in therequest (e.g., included in the request or otherwise determinable basedon information included in the request) that specifies how much of theparticular resource is to be allocated for executing the program code.For example, the developer of a program code may specify in a codeexecution request how much memory (or other computing resources) is tobe allocated for executing his or her program code.

Next, at block 404, the resource manager 150 allocates theuser-specified amount of the computing resource for executing theprogram code. For example, the resource manager 150 may create acontainer that has the user-specified amount of the computing resourcein an instance that is associated with the user and is in the activepool 140A. In another example, the resource manager 150 may select aninstance from the warming pool 130A, assign the selected instance to theuser, and create a container that has the user-specified amount of thecomputing resource in the selected instance.

At block 406, the resource manager 150 monitors the usage of thecomputing resource by the program code during one or more executions ofthe program code. For example, the resource manager 150 may cause theprogram code to be loaded onto the container designated to handle therequest and cause the program code to be executed in the container. Theresource manager 150 may monitor one or more performance characteristicsduring the one or more executions of the program code. Such performancecharacteristics may include error rates, resource utilization, latency,% of resource used, % of resource requested by the user, etc.

At block 408, the resource manager 150 compares the usage of thecomputing resource by the program code to the user-specified amount, andat block 410, the resource manager 150 determines, based on thecomparison, that the user-specified amount of the computing resourceallocated for executing the program code should be adjusted. Forexample, if the user requested 512 MB of memory but only 64 MB was usedon average during the one or more executions of the program code, theresource manager 150 may determine that the user-specified amount may bereduced without significantly affecting the performance of the programcode. On the other hand, if the user requested 512 MB of memory andnearly all of the requested amount was in use during the one or moreexecutions of the program code, the resource manager 150 may determinethat the user-specified amount should be increased to resolve theover-utilization issue.

At block 412, the resource manager 150 provides an indication of how theuser-specified amount should be adjusted. For example, the resourcemanager 150 may provide an email notification to the user indicatingthat the user-specified amount should be increased or decreased by anappropriate amount.

While the routine 400 of FIG. 4 has been described above with referenceto blocks 402-412, the embodiments described herein are not limited assuch, and one or more blocks may be omitted, modified, or switchedwithout departing from the spirit of the present disclosure. Forexample, although the routine 400 is described with reference to asingle computing resource (e.g., memory), similar techniques may beperformed on each of the remaining resource dimensions (e.g., CPU,network, disk, etc.). Further, although the routine 400 is described asmonitoring and comparing a single computing resource on a per-resourcebasis (e.g., comparing the requested amount of memory vs. actually usedamount of memory, comparing the requested amount of processing power vs.actually used amount of processing power, etc.), similar techniques maybe used to perform the routine 400 on a composite basis. For example,the resource manager 150 may compare the requested or allocated amountof the most constrained resource associated with the request with theactual amount of the most constrained resource used by the program codeassociated with the request, and the indication in block 412 may beprovided to the user if the requested or allocated amount of the mostconstrained resource is within a threshold percentage under or over theactual amount of the most constrained resource used by the program code.In another example, the resource manager 150 may calculate the averagepercentage of utilization for each of the resource dimensions, andprovide the indication to the user if the average percentage is under orover a threshold utilization value (e.g., below 10%, above 90%, etc.).The indication provided to the user may also include a breakdown of theover-usage or under-usage of each of computing resource. For example,the resource manager 150 may provide an indication that says, “Youcurrently have your resource sizing dial at 512 MB, which is fine formemory performance because you never use more memory than that, but wehave noticed that you often run out of network resources with thecurrent setting. You may turn the resource sizing dial up by 10% toobtain more network resources and achieve improved code executionperformance.”

Turning now to FIG. 5, a routine 500 implemented by one or morecomponents of the virtual compute system 110 (e.g., the resource manager150) will be described. Although routine 500 is described with regard toimplementation by the resource manager 150, one skilled in the relevantart will appreciate that alternative components may implement routine500 or that one or more of the blocks may be implemented by a differentcomponent or in a distributed manner.

At block 502 of the illustrative routine 500, the resource manager 150allocates a first amount of a computing resource for executing a programcode. For example, the resource manager 150 may create a container thathas the first amount of the computing resource in an instance that isassociated with the user and is in the active pool 140A. In anotherexample, the resource manager 150 may select an instance from thewarming pool 130A, assign the selected instance to the user, and createa container that has the first amount of the computing resource in theselected instance. The computing resource may be memory, CPU, diskspace, or any other computing resource that may be used for executingthe program code on the virtual compute system 110. The first amount maybe determined by the resource manager 150 based on information includedin the request and/or information ascertainable based on the informationincluded in the request. Such information may include the programminglanguage used to code the program code, user type (e.g., high-volumeuser or low-volume user), characteristics of the program code (e.g.,number of lines, number of expensive calls, etc.), etc.

Next, at block 504, the resource manager 150 monitors the usage of thecomputing resource by the program code during one or more executions ofthe program code. For example, the resource manager 150 may cause theprogram code to be loaded onto the container designated to handle therequest and cause the program code to be executed in the container. Theresource manager 150 may monitor one or more performance characteristicsduring the one or more executions of the program code. Such performancecharacteristics may include error rates, resource utilization, latency,% of resource used, % of resource requested by the user, etc.

At block 506, the resource manager 150 determines, based on the usage ofthe computing resource by the program code, that the first amount of thecomputing resource allocated for executing the program code should beadjusted. For example, if 512 MB of memory was allocated for executingthe program code at block 502 but only 64 MB was used on average duringthe one or more executions of the program code, the resource manager 150may determine that the amount allocated for executing the program codemay be reduced without significantly affecting the performance of theprogram code. On the other hand, if 512 MB of memory was allocated forexecuting the program code and nearly all of the allocated amount was inuse during the one or more executions of the program code, the resourcemanager 150 may determine that the amount allocated for executing theprogram code should be increased to resolve the over-utilization issue.

At block 508, the resource manager 150 determines a second amount of thecomputing resource that is different from the first amount, and at block510, the resource manager 150 allocates the second amount of thecomputing resource for executing the program code. In the example inwhich 512 MB was allocated and 64 MB was used on average, the resourcemanager 150 may determine that the amount of allocated memory may besafely reduced to 128 MB without affecting the performance of theprogram code, and allocate 128 MB for executing the program code (e.g.,for future executions of the program code).

While the routine 500 of FIG. 5 has been described above with referenceto blocks 502-512, the embodiments described herein are not limited assuch, and one or more blocks may be omitted, modified, or switchedwithout departing from the spirit of the present disclosure. Forexample, as discussed in connection with FIG. 4, although the routine500 is described with reference to a single computing resource (e.g.,memory), similar techniques may be performed on each of the remainingresource dimensions (e.g., CPU, network, disk, etc.). Further, althoughthe routine 500 is described as monitoring and comparing a singlecomputing resource on a per-resource basis (e.g., comparing thecurrently allocated amount of memory vs. actually used amount of memory,comparing the currently allocated amount of processing power vs.actually used amount of processing power, etc.), similar techniques maybe used to perform the routine 500 on a composite basis. For example,the resource manager 150 may compare the requested or allocated amountof the most constrained resource associated with the request with theactual amount of the most constrained resource used by the program codeassociated with the request, and the determination in block 506 may bebased on whether the requested or allocated amount of the mostconstrained resource is within a threshold percentage under or over theactual amount of the most constrained resource used by the program code.In another example, the resource manager 150 may calculate the averagepercentage of utilization for each of the resource dimensions, and makethe determination based on whether the average percentage is under orover a threshold utilization value (e.g., below 10%, above 90%, etc.).

With reference to FIGS. 6-8, the resource resizing performed by theresource manager 150 according to an example embodiment is illustrated.In the example of FIG. 6, the container 158A is being utilized toprocess incoming code execution requests associated with a particularprogram code. As shown in FIG. 6, the container 158A has an averageresource utilization of 27%. For example, the particular program codehas utilized 27% of the resource(s) allocated to the container 158Aduring one or more executions of the particular program code in thecontainer 158A. The resource manager 150 may compare the resourceutilization to a threshold value (e.g., 75%) and determine that thecurrent resource utilization is too low and that the amount ofresource(s) allocated to the container 158A should be reduced.

In FIG. 7, the resource manager 150 has reduced the amount ofresource(s) allocated to the container 158A for executing the particularprogram code (e.g., at the request of the user associated with theinstance 158 or based on a determination made by the resource manager150 based on utilization), and the resource utilization has increased to40% after one or more additional executions of the particular programcode in the container 158A. Although the resource sizing of an existingcontainer (e.g., container 158A) is adjusted, in another embodiment, anew container having an adjusted amount of resource(s) allocated theretomay be created instead, and the existing container may be drained. Asshown in FIG. 8, the amount of resource(s) allocated to the container158A has further been adjusted to improve the resource utilization to80%. The resource manager 150 may compare the resource utilization levelto the threshold value (e.g., 75%) and determine that further resourceresizing is not necessary, and maintain the resource level of thecontainer 158A at the current level until the resource manager 150 laterdetermines a further resizing is needed. Other components shown in FIGS.6-8 are identical to those shown in FIG. 1 and the details thereof arethus omitted for brevity.

With reference to FIGS. 9-11, the resource resizing performed by theresource manager 150 according to another example embodiment isillustrated. In the example of FIG. 9, the container 159A is beingutilized to process incoming code execution requests associated with aparticular program code. As shown in FIG. 9, the container 159A has anaverage error rate of 90%. For example, 90% of the executions of theparticular program code may have produced one or more errors or failedto successfully execute. The resource manager 150 may compare theresource utilization to a threshold value (e.g., 5%) and determine thatthe current error rate is too high and that the amount of resource(s)allocated to the container 159A should be increased.

In FIG. 10, the resource manager 150 has increased the amount ofresource(s) allocated to the container 159A for executing the particularprogram code (e.g., at the request of the user associated with theinstance 159 or based on a determination made by the resource manager150 based on the error rate), and the error rate has decreased to 20%after one or more additional executions of the particular program codein the container 159A. Although the resource sizing of an existingcontainer (e.g., container 159A) is adjusted, in another embodiment, anew container having an adjusted amount of resource(s) allocated theretomay be created instead, and the existing container may be drained. Asshown in FIG. 11, the amount of resource(s) allocated to the container159A has further been adjusted to improve the error rate to 3%. Theresource manager 150 may compare the error rate to the threshold value(e.g., 5%) and determine that further resource resizing is notnecessary, and maintain the resource level of the container 159A at thecurrent level until the resource manager 150 later determines a furtherresizing is needed. Other components shown in FIGS. 9-11 are identicalto those shown in FIG. 1 and the details thereof are thus omitted forbrevity.

It will be appreciated by those skilled in the art and others that allof the functions described in this disclosure may be embodied insoftware executed by one or more physical processors of the disclosedcomponents and mobile communication devices. The software may bepersistently stored in any type of non-volatile storage.

Conditional language, such as, among others, “can,” “could,” “might,” or“may,” unless specifically stated otherwise, or otherwise understoodwithin the context as used, is generally intended to convey that certainembodiments include, while other embodiments do not include, certainfeatures, elements and/or steps. Thus, such conditional language is notgenerally intended to imply that features, elements and/or steps are inany way required for one or more embodiments or that one or moreembodiments necessarily include logic for deciding, with or without userinput or prompting, whether these features, elements and/or steps areincluded or are to be performed in any particular embodiment.

Any process descriptions, elements, or blocks in the flow diagramsdescribed herein and/or depicted in the attached figures should beunderstood as potentially representing modules, segments, or portions ofcode which include one or more executable instructions for implementingspecific logical functions or steps in the process. Alternateimplementations are included within the scope of the embodimentsdescribed herein in which elements or functions may be deleted, executedout of order from that shown or discussed, including substantiallyconcurrently or in reverse order, depending on the functionalityinvolved, as would be understood by those skilled in the art. It willfurther be appreciated that the data and/or components described abovemay be stored on a computer-readable medium and loaded into memory ofthe computing device using a drive mechanism associated with a computerreadable storage medium storing the computer executable components suchas a CD-ROM, DVD-ROM, or network interface. Further, the componentand/or data can be included in a single device or distributed in anymanner. Accordingly, general purpose computing devices may be configuredto implement the processes, algorithms, and methodology of the presentdisclosure with the processing and/or execution of the various dataand/or components described above.

It should be emphasized that many variations and modifications may bemade to the above-described embodiments, the elements of which are to beunderstood as being among other acceptable examples. All suchmodifications and variations are intended to be included herein withinthe scope of this disclosure and protected by the following claims.

What is claimed is:
 1. A computer-implemented method comprising: asimplemented by one or more computing devices configured with specificexecutable instructions, maintaining a plurality of virtual machineinstances on one or more physical computing devices; receiving aplurality of requests to execute a program code associated with a useron a virtual compute system, the request including informationindicating the program code, the user associated with the program code,and a first amount of a computing resource available on the virtualcompute system to be used to execute the program code; selecting avirtual machine instance from the plurality of virtual machine instancesto be used to execute the program code, the selected virtual machineinstance having at least the first amount of the computing resourceindicated in the plurality of requests; creating one or more containersin the selected virtual machine instance, the one or more containerseach having the first amount of the computing resource indicated in theplurality of requests; causing the program code associated with the userto be loaded onto the one or more containers and executed in the one ormore containers; monitoring a usage of the computing resource by theprogram code during the executions of the program code in the one ormore containers created in the selected virtual machine instance;determining, based on the usage of the computing resource by the programcode, that the first amount indicated in the plurality of requests hassatisfied a resource adjustment condition for a threshold number of theexecutions in the one or more containers; in response to receivingadditional requests including information indicating the program code,the user associated with the program code, and the first amount of thecomputing resource to be used to execute the program code, creating oneor more additional containers in the selected virtual machine instancesuch that the one or more additional containers each have a secondamount of the computing resource that is different from the first amountindicated in the additional requests; and causing the program code to beexecuted in the one or more additional containers having the secondamount of the computing resource.
 2. The computer-implemented method ofclaim 1, further comprising: determining the first amount based on auser-specified amount indicated in the request or other configurationinformation associated with the request, the program code, or the userto execute the program code on the virtual compute system; comparing theusage of the computing resource by the program code to theuser-specified amount indicated in the request; and providing anindication of how the first amount should be adjusted.
 3. Thecomputer-implemented method of claim 2, wherein providing the indicationcomprises one of: (a) indicating that the first amount should beincreased; (b) indicating that the first amount should be increased by afirst adjustment amount; (c) indicating that the first amount should bedecreased; or (d) indicating that the first amount should be decreasedby a second adjustment amount.
 4. The computer-implemented method ofclaim 1, further comprising determining the second amount based on theusage of the computing resource by the program code.
 5. Thecomputer-implemented method of claim 4, wherein determining the secondamount comprises determining the second amount such that the secondamount is within a threshold range specified by a user associated withthe program code.
 6. The computer-implemented method of claim 1, furthercomprising allowing the usage of the computing resource by the programcode to exceed the first amount by an overage amount that is less than amaximum overage amount.
 7. A system adapted to provide low-latencycomputational capacity from a virtual compute fleet, the systemcomprising: an electronic data store configured to store at least aprogram code of a user; and a virtual compute system comprising one ormore hardware computing devices adapted to execute specificcomputer-executable instructions, said virtual compute system incommunication with the electronic data store, and configured to atleast: maintain a plurality of virtual machine instances on one or morephysical computing devices, wherein the plurality of virtual machineinstances comprise a warming pool comprising virtual machine instanceshaving one or more software components loaded thereon and waiting to beassigned to a user, and an active pool comprising virtual machineinstances currently assigned to one or more users; receive a pluralityof requests to execute a program code associated with a user on thevirtual compute system, the plurality of requests each specifying theprogram code, the user associated with the program code, and a firstamount of a computing resource available on the virtual compute systemto be used to execute the program code; select from the warming pool orthe active pool a virtual machine instance to be used to execute theprogram code, the virtual machine instance having at least the firstamount of the computing resource specified in the plurality of requests;create one or more containers in the selected virtual machine instance,the one or more containers each having the first amount of the computingresource specified in the plurality of requests; cause the program codeassociated with the user to be loaded from the electronic data storeonto the one or more containers and executed in the one or morecontainers; determine, based on a determination that the first amount ofthe computing resource specified in the plurality of requests hassatisfied a resource adjustment condition for a threshold number ofexecutions in the one or more containers, that the first amount shouldbe adjusted to improve future executions of the program code; inresponse to receiving additional requests specifying the program code,the user associated with the program code, and the first amount of thecomputing resource to be used for executing the program code, create oneor more additional containers in the selected virtual machine instancesuch that the one or more additional containers each have a secondamount of the computing resource that is different from the first amountspecified in the additional requests; and cause the program code to beexecuted in the one or more additional containers having the secondamount of the computing resource.
 8. The system of claim 7, wherein thevirtual compute system is further configured to provide a notificationto the user comprising one of: (a) indicating that the first amountshould be increased; (b) indicating that the first amount should beincreased by a first adjustment amount; (c) indicating that the firstamount should be decreased; or (d) indicating that the first amountshould be decreased by a second adjustment amount.
 9. A system,comprising: a virtual compute system comprising one or more hardwarecomputing devices executing specific computer-executable instructionsand configured to at least: maintain a plurality of virtual machineinstances on one or more physical computing devices; receive a pluralityof requests to execute a program code associated with a user on thevirtual compute system, the request including information indicating theprogram code, the user associated with the program code, and a firstamount of a computing resource available on the virtual compute systemto be used to execute the program code; select a virtual machineinstance from the plurality of virtual machine instances to be used toexecute the program code, the selected virtual machine instance havingat least the first amount of the computing resource indicated in theplurality of requests; create one or more containers in the selectedvirtual machine instance, the one or more containers each having thefirst amount of the computing resource indicated in the plurality ofrequests; cause the program code associated with the user to be loadedonto the one or more containers and executed in the one or morecontainers; monitor a usage of the computing resource by the programcode during the executions of the program code in the one or morecontainers created in the selected virtual machine instance; determine,based on the usage of the computing resource by the program code, thatthe first amount indicated in the plurality of requests has satisfied aresource adjustment condition for a threshold number of the executionsin the one or more containers; in response to receiving additionalrequests including information indicating the program code, the userassociated with the program code, and the first amount of the computingresource to be used to execute the program code, create one or moreadditional containers in the selected virtual machine instance such thatthe one or more additional containers each have a second amount of thecomputing resource that is different from the first amount indicated inthe additional requests; and cause the program code to be executed inthe one or more additional containers having the second amount of thecomputing resource.
 10. The system of claim 9, wherein the virtualcompute system is further configured to: determine the first amountbased on a user-specified amount indicated in the request or otherconfiguration information associated with the request, the program code,or the user to execute the program code on the virtual compute system;compare the usage of the computing resource by the program code to theuser-specified amount indicated in the request; and provide anindication of how the first amount should be adjusted.
 11. The system ofclaim 10, wherein providing the indication comprises one of: (a)indicating that the first amount should be increased; (b) indicatingthat the first amount should be increased by a first adjustment amount;(c) indicating that the first amount should be decreased; or (d)indicating that the first amount should be decreased by a secondadjustment amount.
 12. The system of claim 9, wherein the virtualcompute system is further configured to determine the second amountbased on the usage of the computing resource by the program code. 13.The system of claim 12, wherein the virtual compute system is configuredto determine the second amount such that the second amount is within athreshold range specified by a user associated with the program code.14. The system of claim 9, wherein the virtual compute system is furtherconfigured to allow the usage of the computing resource by the programcode to exceed the first amount by an overage amount that is less than amaximum overage amount.
 15. A computer-readable, non-transitory storagemedium storing computer executable instructions that, when executed byone or more computing devices, configure the one or more computingdevices to: maintain a plurality of virtual machine instances on one ormore physical computing devices; receive a plurality of requests toexecute a program code associated with a user on a virtual computesystem, the request including information indicating the program code,the user associated with the program code, and a first amount of acomputing resource available on the virtual compute system to be used toexecute the program code; select a virtual machine instance from theplurality of virtual machine instances to be used to execute the programcode, the selected virtual machine instance having at least the firstamount of the computing resource indicated in the plurality of requests;create one or more containers in the selected virtual machine instance,the one or more containers each having the first amount of the computingresource indicated in the plurality of requests; cause the program codeassociated with the user to be loaded onto the one or more containersand executed in the one or more containers; monitor a usage of thecomputing resource by the program code during the executions of theprogram code in the one or more containers created in the selectedvirtual machine instance; determine, based on the usage of the computingresource by the program code, that the first amount indicated in theplurality of requests has satisfied a resource adjustment condition fora threshold number of the executions in the one or more containers; inresponse to receiving additional requests including informationindicating the program code, the user associated with the program code,and the first amount of the computing resource to be used to execute theprogram code, create one or more additional containers in the selectedvirtual machine instance such that the one or more additional containerseach have a second amount of the computing resource that is differentfrom the first amount indicated in the additional requests; and causethe program code to be executed in the one or more additional containershaving the second amount of the computing resource.
 16. Thecomputer-readable, non-transitory storage medium of claim 15, whereinthe instructions further configure the one or more computing devices to:determine the first amount based on a user-specified amount indicated inthe request or other configuration information associated with therequest, the program code, or the user to execute the program code onthe virtual compute system; compare the usage of the computing resourceby the program code to the user-specified amount indicated in therequest; and provide an indication of how the first amount should beadjusted.
 17. The computer-readable, non-transitory storage medium ofclaim 16, wherein providing the indication comprises one of: (a)indicating that the first amount should be increased; (b) indicatingthat the first amount should be increased by a first adjustment amount;(c) indicating that the first amount should be decreased; or (d)indicating that the first amount should be decreased by a secondadjustment amount.
 18. The computer-readable, non-transitory storagemedium of claim 15, wherein the instructions further configure the oneor more computing devices to determine the second amount based on theusage of the computing resource by the program code.
 19. Thecomputer-readable, non-transitory storage medium of claim 18, whereindetermining the second amount comprises determining the second amountsuch that the second amount is within a threshold range specified by auser associated with the program code.
 20. The computer-readable,non-transitory storage medium of claim 15, wherein the instructionsfurther configure the one or more computing devices to allow the usageof the computing resource by the program code to exceed the first amountby an overage amount that is less than a maximum overage amount.